01. Lesson Intro

Header

Lesson Overview

ND036 C1 L1 01 Lesson Intro

Summary

In this lesson, we’ll cover the following topics:

  • The Role of a PM
  • What a PM Does
  • Who PMs work with
  • Identifying Requirements
  • The Roadmap & PRD

Learning Objectives

At the end of this lesson, you’ll be able to:

  • Understand the purpose of the PM role
  • Understand what a PM does during the different stages of the Product Development Cycle
  • Identify key cross-functional partners and customize communications based on understanding of their key priorities
  • Describe different methods for gathering requirements
  • Define the components of a PRD and how to complete each component including documenting requirements

Glossary

Glossary

Term Definition
PRD Product Requirements Doc. A document written by a product manager that describes why a product should be built and what the product should do, as well as how to measure success of the product.
Roadmap A document that describes when specific products and features will be built.
PgM Program Manager. A person who helps a variety of teams (engineering, design, ops, etc) execute against the product roadmap. A program manager keeps the team productive and on track, as well as flags risks.
TPM Technical Program Manager. A more technical program manager, who works closely with engineering teams to execute against the product roadmap. A TPM is more involved in the technical details of software development.
QA Quality Assurance. A team that creates test plans and tests your product to identify and prevent bugs and issues from entering production and affecting users.
PR Public Relations. A team that helps you tell the story about your product with the public and media.
i18n Internationalization. A team and/or process that helps you bring your product to new markets around the globe.

Next Concept